Latency-Sensitive Network-Traffic Quality of Service

ABSTRACT

A telecommunication system can include routing devices, a bearer-management device, and a policy-management device. The bearer-management device can receive a request from a terminal to create a specialized bearer (SB) for a non-audio, non-video media type. The bearer-management device can determine that the request is associated with an authorized user, and then send a setup message comprising a Quality of Service (QoS) indicator to the policy-management device. The policy-management device can create the SB permitting data exchange between the terminal and a routing device. The SB can have QoS characteristics associated with the QoS indicator. In some examples, the terminal can receive a network address, determine an associated network port, and send a SIP INVITE message indicating the non-audio, non-video media type. The terminal can then exchange data on the network port with a peer network terminal.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not applicable

BACKGROUND

Modern telecommunications networks such as cellular telephone networkscan support a variety of types of session, such as voice, video, ormessaging. Second-generation (2G) and third-generation (3G) cellularnetworks such as Global System for Mobile Communications (GSM) networksor Universal Mobile Telecommunications System (UMTS) networks generallycarry streaming media over circuit-switched (CS) connections.Fourth-generation (4G) cellular networks such as Long Term Evolution(LTE) (including LTE-Advanced) networks generally carry streaming mediaover packet-switched (PS) connections. Those PS connections may alsocarry non-streaming types of data, e.g., file downloads. Many cellularnetworks are standardized by the Third-Generation Partnership Project(3GPP).

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features. For brevity of illustration, in thediagrams herein, an arrow beginning with a diamond connects a firstcomponent or operation (at the diamond end) to at least one secondcomponent or operation that is or can be, in at least one example,included in the first component or operation.

FIG. 1 illustrates an example telecommunications system providingspecialized bearers (SBs).

FIG. 2 illustrates an overview of nodes and devices involved in bearerselection for a terminal.

FIG. 3 is a block diagram illustrating components of a system thatprovides bearer selection according to some implementations.

FIG. 4A illustrates a portion of an example bearer-selection processperformed in a telecommunications network.

FIG. 4B illustrates another portion of the example bearer-selectionprocess of FIG. 4A.

FIG. 5 illustrates an example process for creating multiple specializedbearers.

FIG. 6 illustrates an example bearer-selection process.

FIG. 7 illustrates an example process for creating specialized bearers.

FIG. 8 illustrates an example process of forwarding packets viaspecialized bearers.

FIG. 9 illustrates an example process of forwarding packets viaspecialized bearers using Internet Protocol (IP)-based Quality ofService (QoS).

FIG. 10 illustrates an example authorization-verification andbearer-creation process.

FIG. 11 illustrates an example process of creating multiple specializedbearers for a channel.

FIG. 12 illustrates an example process of managing a session associatedwith a specialized bearer.

FIG. 13 illustrates example processes of authorizing users anddetermining setup messages.

FIG. 14 illustrates an example process for communicating via aspecialized bearer.

FIG. 15 illustrates an example process for communicating via a secondspecialized bearer.

FIG. 16 illustrates an example process of sending data via a specializedbearer.

FIG. 17 illustrates an example process of requesting a specializedbearer.

DETAILED DESCRIPTION Overview

This disclosure describes, in part, a telecommunications networkconfigured to provide improved QoS for latency-sensitive traffic thatdoes not have a guaranteed bit rate (GBR). Such traffic can be carriedby an appropriately-configured bearer. A bearer is an identified logicalconnection for conveying data in a manner determined by the bearer. Forexample, a bearer can have particular QoS or throughput (bits persecond, bps) characteristics. A terminal can have one or more bearersopen concurrently via a single radio connection. Bearer managementaccording to some examples herein can include any of: creation ofbearers, termination of bearers, assignment of bearers to terminals ortraffic flows, or selection of bearers to carry particular types oftraffic. Bearer assignment or selection can be performed, e.g., whenbearers are created or terminated, or at handover or other changes ofstate of a terminal.

Some network traffic is latency-sensitive, for example, transmissionsduring a multiplayer game. In some prior schemes, that traffic is routedin the same way as non-latency-sensitive network traffic, such asWeb-browsing traffic. In some examples herein, low-latency networkcommunications (e.g., cellular data communications) are provided forservices that would not be able to access low-latency communicationservices in some prior schemes. In some examples herein, traffic to orfrom terminals associated with authorized users is routed viaspecialized bearers that have low-latency QoS parameters. An app on aterminal can request a network node to create such a bearer, then usethat bearer to exchange information over a connection having lowerlatency than might otherwise be available.

Examples of bearers can include, in LTE, data radio bearers (DRBs)between the terminal and an eNodeB, S1 bearers between the eNodeB and aServing Gateway (S-GW), or Evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN) Radio Access Bearers (E-RABs) between the terminal andthe S-GW. A bearer via one or more network(s) between a first node ordevice and a second node or device can include or consist of otherbearers, each spanning part of a path through the network between thefirst node or device and the second node or device. For example, anE-RAB can include or consist of a DRB and a corresponding S1 bearer. Insome examples, a bearer can carry a service data flow (SDF, 3GPP 23.203)having defined flow characteristics, or an aggregate of SDFs. In someexamples, a bearer carries traffic for a particular packet data network(PDN), e.g., the Internet or an IP Multimedia Subsystem (IMS), and thattraffic includes multiple SDFs, e.g., one for email and another forstreaming video.

As used herein, a “terminal” is a communication device, e.g., a cellulartelephone or other user equipment (UE), configured to perform, orintercommunicate with systems configured to perform, techniquesdescribed herein. Terminals can include, e.g., wireless or wired voice-or data-communication devices. A terminal can be a device that includesa user interface (e.g., as does a smartphone), or can be a device thatdoes not include a user interface. For example, a streaming serverconfigured to provide audio or visual content on demand can be aterminal. Such a terminal may not include a user interface, and mayinstead respond to other terminals that form queries and send thosequeries to the server in response to actions taken via interfaces atthose other terminals. A terminal can be, e.g., a cellular phone,smartphone, tablet computer, personal digital assistant (PDA), personalcomputer (PC), laptop computer, media center, work station, etc.

The terms “session” and “communication session” as used herein include acommunications path for bidirectional exchange of data among two or moreterminals. Example sessions include voice and video calls, e.g., bywhich human beings converse; data communication sessions, e.g., betweentwo electronic systems or between an electronic system and auser-interface device in use by a human being; or a Rich CommunicationSuite (RCS) session. Sessions can be carried, e.g., by cellular or datanetworks, e.g., LTE or IEEE 802.11 (WIFI). Other examples of networksare discussed below.

Some examples herein relate to low-latency traffic. Some examples hereinrelate to traffic other than audio or video traffic. Some examplesherein relate to communications sessions involving the exchange ofmultiple types of data, e.g., voice, text, and state.

Subsection headers in this Detailed Description are solely forconvenience in reading. No limitations are implied by the presence orarrangement of the subsection headers, or by the separation of featuresbetween those subsections. Some examples include features from only onesubsection. Some examples include features from more than onesubsection.

As used herein, the term “unique identifier” and similar terms encompassboth truly unique identifiers (e.g., Ethernet MAC addresses that areunique by construction, or Version No1 UUIDs) and identifiers with anegligible probability of collision (non-uniqueness) (e.g., SHA256hashes of data uniquely identifying an object, or Version 4 UUIDs).

As used herein, a “random” value can be a truly random value, e.g.,measured from physical phenomena, or a pseudorandom value. Examples ofrandom values include cryptographically-strong random numbers.

Illustrative Telecommunications Networks and Components

FIG. 1 illustrates an example telecommunication system 100 and shows anoverview of nodes and devices involved in provision of bearer-managementservices to terminals. The telecommunication system 100 includesterminals 102(1)-102(N) (individually or collectively referred to hereinwith reference 102), N≥1. A terminal 102 may be or include a cellularphone or other type of terminal such as those described above.

Terminals 102 can be configured to initiate or receive communicationsessions, such as a voice call, a video call, or another sort ofsynchronous communication. Initiation of such communications may involvecommunication clients and Session Initiation Protocol (SIP, RFC 3261)clients communicatively connected with components of thetelecommunication system 100, e.g., session-control node 104.Session-control node 104 can be part of an application network, e.g., anIMS network, the Internet or a subset thereof (e.g., a virtual privatenetwork, VPN), or another network providing services to terminal 102.The application network can also be referred to as an “upper-level”network that uses the services provided by access networks (FIG. 2) tocommunicate with terminals 102. System 100 can include or be connectedwith any number of access networks or any number of applicationnetworks. In various embodiments, the session-control node 104represents component(s) of an IMS core network.

Signaling messages are shown as being carried over signaling path 106,which can represent a dedicated signaling link (e.g., a Signaling System7, SS7, link) or a flow of signaling data across a link shared withnon-signaling traffic (e.g., ISUP over SIGTRAN, or non-ITU TCP/IP-familyprotocols such as SIP). SIP can be used to establish and managecommunication sessions. SIP is an IP-based protocol, so terminal 102exchanges SIP messages with session-control node 104 via signaling path106 carrying IP packets. Session-control node 104 can include, e.g., aproxy call session control function (P-CSCF) via which terminal 102 canaccess IMS services. Other signaling protocols can be additionally oralternatively be used, e.g., over Web Real-Time Communication (WebRTC)links. In some examples, session-control node 104 can include an H.323multipoint control unit, and terminal 102 can exchange H.225.0 signalingmessages with session-control node 104 via signaling path 106, e.g., formultimedia conferencing.

Each terminal 102 can exchange non-signaling data (for brevity, “media”)via at least one respective media path with routing device(s) 108. Shownare M routing devices 108(1)-108(M) (individually or collectivelyreferred to herein with reference 108), M≥1. Terminal 102(1) exchangesmedia with routing device 108(1) via media path 110, and terminal 102(N)exchanges media with routing device 108(M) via media path 112. Routingdevices 108 can in turn route the media to other terminals or networkdevices (omitted for brevity). Each terminal 102 is shown as attached toa respective routing device 108, but this is not limiting. In someexamples, N=M; in some examples, N≠M. An individual routing device 108can connect with any number ≥0 of terminals. In some examples, eachterminal 102 is connected to either zero or one routing devices 108 atany given time. In some examples, at least one terminal 102 is connectedto more than one routing device 108 concurrently.

In some examples, session-control node 104 provides voice-calling,video-calling, or data services. Session-control node 104 can providedifferent QoS levels to different services. In some examples, QoS levelsare identified by LTE QoS Class Identifiers (QCIs). QCIs can be used todefine QoS for individual bearers. Each QCI defines particular latency,packet priority, and packet-loss rate requirements. For example, an IMScore can provide voice-over-LTE (VoLTE) data-transport services at QCI1, video-over-LTE (ViLTE) video data-transport services at QCI 2, IMSsignaling at QCI 5, and non-GBR packet data at QCI 6.

However, QCI 6, in some prior schemes, permits latency of up to 300 ms.User(s) of two or more terminals 102 may wish to exchange non-GBR packettraffic, but without incurring the latency penalty of QCI 6. In someexamples, accordingly, the system 100 (or components thereof, andlikewise throughout the discussion of this figure) establishes aspecialized bearer (SB) 114 between terminal 102(1) and routing device108(1), and an SB 116 between terminal 102(N) and routing device 108(M).SB 114 carries media path 110, and SB 116 carries media path 112. TheSBs provide predetermined QoS levels (e.g., associated withpredetermined QCIs) for packet data flows, such as media-packet flowsassociated with apps other than system dialers running on terminals 102.In some examples, the SBs 114, 116 provide a transparent connection toan application network, e.g., including a media server 118 (shown inphantom), permitting low-latency traffic exchange with that applicationnetwork.

In some examples, multiple routing devices 108 can establish bearersbetween themselves to carry traffic from SBs. In the illustratedexample, routing devices 108(1), 108(M) can exchange traffic via bearer120. Terminals 102(1) can send low-latency media to terminal 102(N) viaSB 114, bearer 120, and SB 116, and vice versa. Bearer 120 can be orinclude an SB or another type of bearer or packet flow. In someexamples, traffic over bearer 120 can carry an indication of the QoSassociated with SBs 114, 116, e.g., an IP Differentiated Services CodePoint (DSCP) value.

In some examples, SBs 114, 116 are created on request of the respectiveterminals 102(1), 102(N). In some examples, a bearer-management device122, e.g., a P-CSCF, receives requests to create SBs, e.g., a requestfrom terminal 102(1) to create SB 114. Bearer-management device 122determines that the request is associated with an authorized user, e.g.,by exchanging messages with an information server 124. Informationserver 124 can include, e.g., a home location register (HLR)/homesubscriber server (HSS). After determining that the user is authorized,bearer-management device 122 sends a setup message to apolicy-management device 126, e.g., a policy control rules function(PCRF) node. Policy-management device 126 interacts with routing devices108 to establish the SBs, e.g., SB 114. Other examples ofbearer-management device 122 and policy-management device 126 arediscussed herein.

As used herein, a message “sent to,” “transmitted to,” or “transmittedtoward” a destination, or similar terms, can be sent directly to thedestination, or can be sent via one or more intermediate network nodesor devices to the destination. Those intermediate network nodes ordevices can include routing device(s) 108. Similarly, a message“received from” a destination can be received directly from thedestination, or can be received via one or more intermediate networknodes or devices from the destination. A message passing through one ormore intermediate network nodes or devices can be modified by thosenetwork nodes or devices, e.g., by adding or removing framing, bychanging routing information, or by changing a presentation of at leastpart of the message, e.g., from a SIP start-line to a SIP header or viceversa. As used herein, a “reply” message is synonymous with a “response”message. The term “reply” is used for clarity, e.g., when discussingreply messages sent in response to the receipt of messages.

Any of session-control node 104, routing device(s) 108,bearer-management device 122, information server 124, andpolicy-management device 126 can be or include a server or server farm,multiple, distributed server farms, a mainframe, a work station, a PC, alaptop computer, a tablet computer, an embedded system, or any othersort of device or devices. In one implementation, one or more of thesemay represent a plurality of computing devices working in communication,such as a cloud-computing node cluster. Examples of such components aredescribed below with reference to FIG. 3.

FIG. 2 illustrates an example telecommunication system 200 (which canrepresent system 100). Elements shown in FIG. 2 can representcorresponding elements shown in FIG. 1. Terminal 202, e.g., userequipment, communicates with access network 204 of the telecommunicationsystem 200. Access network 204 can be any type of access network, e.g.,LTE or WIFI. For example, voice calls can be carried over the firstaccess network using VoLTE or voice-over-WIFI (VoWIFI). IMS 206communicates with access network 204 and provides media-handlingservices, e.g., to route video or voice data. For example, IMS 206 canprovide services permitting terminal 202 to communicate with peertelecommunications network 208 (shown in phantom), e.g., with a node 210thereof, such as a server or terminal. Peer network 208 can be operatedby the same operator as IMS 206 or by a different operator. For example,IMS 206 and peer network 208 can be two IMSes operated by the sameoperator, or IMSes operated by respective, different operators. In someexamples, peer network 208 is a PSTN or a 2G, 3G, or LTE cellularnetwork. In some examples, peer network 208 is the Internet or anotherpacket network.

In the illustrated example, access network 204 includes a controller212, e.g., a mobility management entity (MME) associated with an LTEaccess network. Access network 204 includes a base station 214, e.g., anLTE eNodeB 4G base station, WIFI wireless access point (WAP), or otheraccess point, that provides connectivity to access network 204. Accessnetwork 204 also includes a packet data network gateway 216 (“PGW” or“PDN-GW”) that conveys traffic between terminal 202 and networks outsidethe access network, e.g., IMS 206 or peer network 208. PGW 216 canrepresent a routing device 108. Access network 204 also includes a PCRF218 (which can represent policy-management device 126), e.g., a serveror other network device responsible for distributing policy informationor interacting with policy-related network functions outside accessnetwork 204. Access network 204 can include more than one of any ofthese components, or can include other components not shown.

In the illustrated example, IMS 206 includes a P-CSCF 220. IMS 206 alsoincludes an interrogating CSCF (I-CSCF) 222, a serving CSCF (S-CSCF)224, and a HLR/HSS 226. These components can perform functions describedin 3GPP or other pertinent specifications. In some examples, P-CSCF 220can additionally or alternatively perform functions described herein,e.g., with reference to FIGS. 3-13. For example, P-CSCF 220 cancommunicate with PCRF 218 as described below. IMS 206 also includes anapplication server (AS) 228 configured to perform functions describedherein, e.g., with reference to FIGS. 3-13. For example, AS 228 cancommunicate with PCRF 218 as described below, or can provide networkrelaying services as described below. In some examples, the AS 228 is ananchoring network device and proxies signaling traffic for acommunication session, e.g., operating as a SIP proxy or back-to-backuser agent (B2BUA). The AS 228 (or other anchoring network device, andlikewise throughout) can provide session-control services to terminal202.

In the illustrated example, a signaling path 230 of a communicationsession passes through base station 214 and PGW (routing device) 216 inaccess network 204, and then through P-CSCF 220, I-CSCF 222, S-CSCF 224,and AS 228 in IMS 206, as indicated by the dash-dot arrow (in some otherexamples, I-CSCF 222 is omitted or bypassed). After AS 228, the examplesignaling path passes back through S-CSCF 224 to a network node of peertelecommunication system 208, shown as a proxy 232. Proxy 232 caninclude, e.g., an S-CSCF, I-CSCF, or BGCF.

In the illustrated example, a media path 234 of the communicationsession passes through base station 214 and PGW 216 in access network204. PGW 216 forwards the traffic to or from peer network 208. In theillustrated example, traffic between terminal 202 and peer node 210 isexchanged between PGW 216 and a peer routing device 236 of peer network208.

Although peer network 208 and its components are shown in phantom, insome examples not depicted, at least one component of peer network 208can be part of system 200. Moreover, in other examples not depicted, oneor both of proxy 232 and peer routing device 236 may not be present. Insome examples, peer network 208 is the Internet, node 210 is anon-IMS-connected device, and PGW 216 exchanges traffic directly withnode 210. This can support low-latency use cases such as real-timemessaging, computer-mediated competition, or over-the-top (OTT) videocalling.

Data exchanges in computer-mediated competition or other networkinteractions can have a star topology, a mesh topology, or othertopologies. In a star topology, each terminal 102, 202 interacts with acommon media server 118 (e.g., node 210). In a mesh topology, at leastone terminal 102, 202 exchanges data with another terminal 102, 202without passing through media server 118 or a similar device.

In the illustrated example, media path 234 between terminal 202 and PGW216 is carried via a specialized bearer (SB) 238. SB 238 can be orinclude, e.g., an LTE Evolved Packet System (EPS) dedicated bearerproviding desired QoS characteristics, e.g., lower latency than trafficon a default bearer. SB 238 can include a DRB between terminal 202 andbase station 214, an S1 bearer between base station 214 and an LTE S-GW(omitted for brevity), and an S5/S8 bearer between the S-GW and PGW 216.In some examples, SB 238 can have LTE QCI 3.

The devices and networks illustrated in FIG. 2 can be examples of thedevices and networks illustrated in FIG. 1 and described above. Forinstance, terminal 202 can represent a terminal 102; PGW 216 canrepresent a routing device 108; P-CSCF 220, AS 228, or PCRF 218 canrepresent bearer-management device 122; PCRF 218 can representpolicy-management device 126; HLR/HSS 226 can represent informationserver 124; signaling path 230 can represent signaling path 106; or SB238 can represent SB 114 or 116. Accordingly, the descriptions of thedevices and networks of FIG. 1 apply to the devices and networks of FIG.2. The devices and networks of FIG. 2 may cooperate to accomplish mediarouting, e.g., as shown in FIG. 1 and described herein. They may alsocooperate to accomplish the initiation of a communication session ofterminal 202. Techniques described herein with respect to originatingcommunication sessions can also be used for receiving (terminating)sessions or for exchanging messages sent during an established phase ofa communication session, in some examples.

Example cellular access networks 204 can include a GSM or UMTS network;a universal terrestrial radio network (UTRAN) or an GSM Enhanced Datarates for GSM Evolution (EDGE) radio access network (GERAN); an E-UTRAN(e.g., LTE); an Evolution-Data Optimized (EVDO), Advanced LTE (LTE+),Generic Access Network (GAN), Unlicensed Mobile Access (UMA), GPRS,EDGE, High Speed Packet Access (HSPA), or evolved HSPA (HSPA+) network.Example non-cellular access networks 204 can include a WIFI (IEEEN2802.11), BLUETOOTH (IEEE N2802.15.1), or other local-area network(LAN) or personal-area network (PAN) access networks, e.g., in the IEEEN2802.1* family, a satellite or terrestrial wide-area access networksuch as a wireless microwave access (WIMAX) network, a wired networksuch as the PSTN, an optical network such as a Synchronous OpticalNETwork (SONET), or other fixed wireless or non-wireless networks suchas Asynchronous Transfer Mode (ATM) or Ethernet, e.g., configured totransport IP packets, e.g., IPv4, IPv6, or any other evolution of anIP-based technology.

In some examples, access network 204 can include a base station (e.g.,an eNodeB or gNodeB), a radio network controller (RNC) (e.g., for UMTSaccess networks), or other elements. A cellular network or a wirelessdata network may use any sort of air interface, such as a code divisionmultiple access (CDMA), time division multiple access (TDMA), frequencydivision multiple access (FDMA), or orthogonal frequency divisionmultiple access (OFDMA) air interface.

The telecommunication system 200 may also include a number of devices ornodes not illustrated in FIG. 2. Nonlimiting examples of such devices ornodes include an Access Transfer Gateway (ATGW), a serving GPRS supportnode (SGSN), a gateway GPRS support node (GGSN), a session bordercontroller (SBC), a visitor location register (VLR), an ISBC or IBCF, aBGCF, or a media gateway (MGW), an S-GW, or a non-3GPP-accessinterworking function (N3IWF). Similarly, throughout this disclosure,other nodes or devices can be used in conjunction with listed nodes ordevices. For example, a telecommunications network can include many corenetwork nodes or devices, only some of which implement functionsdescribed herein for core network nodes or devices. IMS 206 may furtherinclude a number of devices or nodes not illustrated in FIG. 2, such asa presence server and one or more additional CSCFs. A core network ofthe telecommunications network may be a GPRS core network or an evolvedpacket core (EPC) network, or may include elements from both types ofcore networks.

FIG. 3 is a block diagram illustrating a system 300 permitting mediatransport according to some implementations. The system 300 includes aterminal 302, e.g., a wireless phone or other terminal such as aterminal 102, 202, coupled to a server 304 via a network 306. The server304 can represent a bearer-management device 122 (e.g., P-CSCF 220), apolicy-management device 126 such as PCRF 218, an information server 124(e.g., HLR/HSS 226), or another control device or information server ofa telecommunications network.

The network 306 can include one or more networks, such as a cellularnetwork and a data network. In some examples, network 306 may includeany network configured to transport IP packets, e.g., IPv4, IPv6, or anyfuture IP-based network technology or evolution of an existing IP-basednetwork technology. For example, the network 306 can include one or morecore network(s) connected to terminal(s) via one or more accessnetwork(s) (e.g., access network 204).

Terminal 302 can include one or more computer readable media (CRM) 308,such as memory (e.g., random access memory (RAM), solid state drives(SSDs), or the like), disk drives (e.g., platter-based hard drives),another type of computer-readable media, or any combination thereof.Terminal 302 can include one or more processors 310 configured toexecute instructions stored on CRM 308. The CRM 308 can be used to storedata and to store instructions that are executable by the processors 310to perform various functions as described herein. The CRM 308 can storevarious types of instructions and data, such as an operating system,device drivers, etc. The processor-executable instructions can beexecuted by the processors 310 to perform the various functionsdescribed herein.

The CRM 308 can be or include computer-readable storage media.Computer-readable storage media include, but are not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other tangible, non-transitory medium which can be used to storethe desired information and which can be accessed by the processors 310.Tangible computer-readable media can include volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information, such as computer readableinstructions, data structures, program modules, or other data.

Processor(s) 310 can include, e.g., e.g., one or more processor devicessuch as central processing units (CPUs), microprocessors,microcontrollers, field-programmable gate arrays (FPGAs),application-specific integrated circuits (ASICs), programmable logicdevices (PLDs), programmable logic arrays (PLAs), programmable arraylogic devices (PALs), or digital signal processors (DSPs). For brevity,processor 310 and, if required, CRM 308, are referred to for brevityherein as a “control unit.” For example, a control unit can include aCPU or DSP and instructions executable by that CPU or DSP to cause thatCPU or DSP to perform functions described herein. Additionally oralternatively, a control unit can include an ASIC, FPGA, or other logicdevice(s) wired (physically or via blown fuses or logic-cellconfiguration data) to perform functions described herein. Otherexamples of control units can include processor 324 and, if required,CRM 326, discussed below. Accordingly, functions described as carriedout by processor(s) 310 in response to instructions stored on a CRM 308can additionally or alternatively be performed by a control unitconfigured to perform functions described herein without readinginstructions to do so from CRM 308.

For brevity, discussions of functions performed “by” module(s) refer, inthe context of processor-executable instructions, to functions performedin response to processor-executable instructions of the referred-tomodule(s). In the context of FPGAs or other control units not usingprocessor-executable instructions, discussions of functions performed“by” module(s) refer to functions performed by the special-purpose logicor other configuration of those module(s).

Terminal 302 can further include a user interface (UI) 312, e.g.,including an electronic display device, a speaker, a vibration unit, atouchscreen, or other devices for presenting information to a user andreceiving commands from the user, e.g., under control of processor(s)310. Terminal 302 can further include one or more communicationsinterface(s) 314 configured to selectively communicate (wired orwirelessly) via the network 306, e.g., via an access network, undercontrol of the processor(s) 310.

CRM 308 can include processor-executable instructions of a clientapplication 316. The client application 316, e.g., a native or otherdialer, can permit a user to originate and terminate communicationsessions associated with the terminal 302, e.g., a wireless phone. Theclient application 316 can additionally or alternatively include an SMS,RCS, or presence client, or a client of another telephony serviceoffered by the server 304. The client application 316 can additionallyor alternatively include an app a Web browser configured to communicatevia WebRTC or other non-3GPP protocols.

CRM 308 can additionally or alternatively store processor-executableinstructions of a specialized application 318, e.g., a smartphone app orother program that, when executed by processor 310, communicates viaspecialized bearers (SBs) as described herein, e.g., with reference toFIGS. 14-17. Specialized application 318 is referred to subsequently,for brevity and without limitation, as an “app.”

CRM 308 can additionally or alternatively store identificationinformation 320 associated with terminal 302 or a user thereof. Forexample, CRM 308 can include a subscriber identity module (SIM) cardstoring, as at least part of identification information 320, anInternational Mobile Subscriber Identity (IMSI), a Mobile SubscriberInternational Subscriber Directory Number (MSISDN), a username, ane-mail address, or another type of identification information.

In some examples, server 304 can communicate with (e.g., iscommunicatively connectable with) terminal 302 or other devices via oneor more communications interface(s) 322, e.g., network transceivers forwired or wireless networks, or memory interfaces. Example communicationsinterface(s) 322 can include ETHERNET or FIBRE CHANNEL transceivers,WIFI radios, or DDR memory-bus controllers (e.g., for DMA transfers to anetwork card installed in a physical server 304).

The server 304 can include one or more processors 324 and one or moreCRM 326. The CRM 326 can be used to store processor-executableinstructions of a bearer-management module 328 and a session-operationsmodule 330. The processor-executable instructions can be executed by theone or more processors 324 to perform various functions describedherein, e.g., with reference to FIGS. 3-13. In some examples, server 304can be configured to, e.g., by executing the processor-executableinstructions, perform functions described herein with reference to FIGS.3-13.

Illustrative Operations

FIGS. 4A and 4B are dataflow diagrams together illustrating an exampleprocess 400 for bearer management (e.g., creation), and related dataitems. Process 400 can be performed, e.g., by a control device such as aserver 304 of a telecommunications system 300, e.g., includingcommunications interface 322 and at least one processor 324. Server 304can be or include, e.g., a bearer-management device 122 such as P-CSCF220. In some examples, the server 304 includes control unit(s)configured to perform operations described below, e.g., in response tocomputer program instructions of the bearer-management module 328 or thesession-operations module 330. For example, operations 426 and 454 canbe performed by (e.g., in response to instructions of, as noted above)the session-operations module 330 and the remaining operations can beperformed by the bearer-management module 328. Alternatively, all theoperations of process 400 can be performed by the bearer-managementmodule 328.

Process 400 can be performed by bearer-management device 122communicatively connectable with one or more routing devices 108, e.g.,PGWs, and with a policy-management device 126. Process 400 can includeproviding services to one or more terminals 302, e.g., connected to oneor more routing devices 108. In some examples, the one or more routingdevices 108 are configured to convey traffic between a first specializedbearer (SB) 406 and a second SB 434, both discussed below.

Operations shown in FIG. 4 and in FIGS. 5-17, discussed below, can beperformed in any order except when otherwise specified, or when datafrom an earlier step is used in a later step. For clarity ofexplanation, reference is herein made to various components shown inFIGS. 1-3 that can carry out or participate in the steps of the examplemethods. It should be noted, however, that other components can be used;that is, example method(s) shown in FIGS. 4-17 are not limited to beingcarried out by the identified components, and are not limited toincluding the identified operations or messages.

At 402, the control unit can receive, from a first network terminal 102(or 202, 302, and likewise throughout this discussion) via acommunications interface, a first request 404 to create a first SB 406(bearers are depicted using hexagons throughout FIGS. 4-17). The firstrequest 404 can identify a first communication channel. For example, thefirst request 404 can include identification 408 of the firstcommunication channel. In some examples, the first request can be orinclude a SIP INVITE request or other SIP or non-SIP request. Theidentification 408 can include, e.g., a network address, port, oraddress/port pair; a peer address, port, or address/port pair; a uniqueidentifier; an address or other identifier of a multicast group; adomain name; or a Uniform Resource Identifier (URI), e.g., a tel: URI.In some examples, the identification 408 is not an identifier of a partyreachable via VoLTE or ViLTE from the server 304. In some examples, theidentification 408 is not an identifier of a party reachable via VoLTEor ViLTE from the first network terminal 102, 202, 302. In someexamples, identification 408 can be shared among multiple users whodesire to exchange low-latency traffic. In some examples, identification408 is human-readable or -expressible, so that multiple users cancommunicate identification 408 amongst each other, e.g., verbally or inwriting. For example, identification 408 can be expressed as a string ofat most n characters, e.g., n=8, 10, 16, 20, 32, or 64; as a string ofwords using, e.g., the PGP word list; or as a series of at most nnumbers, e.g., n=4, 5, 6, 8, or 10.

At 410, the control unit can make a first determination 412 that thefirst request 404 indicates a first predetermined media type 414. Solelyfor brevity hereafter, “mtype” is used as an abbreviation for“predetermined media type.” For example, the control unit can locatedata in first request 404 indicating the first mtype 414. The controlunit can then compare the data to a stored list of one or more mtypes,and store data of the first determination 412 indicating that the firstmtype 414 is found in the stored list.

The data in first request 404 can include, e.g., a header, aheader-field value (e.g., a value of a SIP Content-Type header), or abody element. A body element can include, e.g., an SDP m=line, or thevalue thereof, or the value in an Rx-interface (Diameter) Media-Type AVP(3GPP TS 29.214 v15.4.0 § 5.3.19). In some examples, the first mtype 414is not an audio media type, and the first mtype 414 is not a video mediatype. For example, the first mtype 414 can include an SDP m=mediadescription type other than “audio” or “video”; or the first mtype 414can include an Rx Media-Type AVP other than AUDIO or VIDEO.

In some examples, the first mtype 414 can be, e.g., a predeterminedvalue associated with low-latency traffic, e.g., an SDP m=line value of“zephyr” or “fast-data”; a SIP Content-Type of “application/fast-data”;or an Rx Media-Type value of 42 (or another predetermined value between7 and 0xFFFF FFFE, inclusive). In some examples, first mtype 414 has avalue different from any or all of: the media values listed in RFC 4566§ 8.2.1 (SDP “media” values) and the values listed in in 29.214 § 5.3.19for the Media-Type AVP.

At 416, the control unit can make a second determination 418 that thefirst request 404 is associated with a first authorized user. In someexamples, operation 416 is performed before operation 410 instead ofafter. For example, the first request can include user information,e.g., a SIP From: header value, a source IP address or address/portcombination, an IMSI, or another identifier of a user associated withterminal 102. The control unit can retrieve, from information server124, authorization information associated with the user information. Forexample, the control unit can query the information server 124 viaDiameter to retrieve an AVP indicating whether the user is authorized tocreate the first SB 406.

Some prior schemes, such as some VoLTE implementations, do not applyuser-based service-authorization control to SIP requests at the P-CSCFor other bearer-management device 122. These schemes permit anySIP-connected user to send SIP requests, e.g., to the IMS Access PointName (APN), via a terminal 102 known to information server 124 andregistered with bearer-management device 122. By contrast, some examplesusing operation 416 permit controlling access to SBs. This can increasenetwork robustness by reducing the chance that too many SBs will berequested or used concurrently.

At 420, the control unit can send a first setup message 422 via thecommunications interface to a policy-management device 126, e.g., PCRF218. The control unit can perform operation 420 in response to the firstdetermination 412 and to the second determination 418. The first setupmessage 422 can request establishment of the first SB 406. The firstsetup message 422 can include a first QoS indicator 424. In someexamples, the first setup message 422 includes an Rx Diameter AA-Request(AAR) message carrying a Media-Type or QoS-Information AVP associatedwith the requested low-latency traffic characteristics. In someexamples, the AAR can include information directly indicating an LTE QCI(or other QoS parameters for first SB 406), e.g., a QoS-Class-IdentifierAVP. In some other examples, the AAR can include information thepolicy-management device 126 will use to determine the QCI (or other QoSparameters). In some examples using QCIs, the QCI can be anoperator-specific value or a spare value. For example, the first QoSindicator 424 can indicate a QCI E {10-64, 67, 68, 71-74, 76-78, 81,86-127, 128-254}; or a QCI in the range 128-254 (3GPP TS 29.212 v15.3.0§ 5.3.17).

At 426, the control unit can send, to the first network terminal, afirst completion message 428 indicating establishment of the first SB406. First completion message 428 can include, e.g., a SIP 200 OK orother 1xx or 2xx response. In some examples, the control unit sendsfirst completion message 428 independently of any other terminals 102that may be participating in or communicating via the firstcommunications channel. For example, each terminal 102 can send anINVITE and receive an OK with respect to its own SB 114.

FIG. 4B shows further operations of process 400 performed, e.g., by acontrol unit of bearer-management device 122. Operation 426 is followedby operation 430 in the illustrated example. In some examples, at leastone of operations 402-426 is followed by operation 430. In someexamples, operations of FIG. 4B are performed before operations of FIG.4A, and operation 454 is followed by operation 402. In some examples,operations of FIGS. 4A and 4B are performed in parallel, e.g., bymultiple control units or by timesliced operation of a single controlunit. Accordingly, operations of FIG. 4A can be interleaved withoperations of FIG. 4B in any combination. This is also true of FIGS. 4A,4B, and 5; FIGS. 10 and 11; and FIGS. 14 and 15.

At 430, the control unit can receive, from a second network terminal102, 202, 302 via the communications interface, a second request 432 tocreate a second SB 434. The second request 432 can identify a secondcommunication channel. For example, the second request 432 can includeidentification 436 of the second communication channel.

In some examples, the first communication channel is communicativelyconnected with the second communication channel. For example, in acommunication between first and second terminals, the firstcommunication channel can be identified (#408) by the address/port atthe first terminal, and the second communication channel can beidentified (#436) by the address/port at the second terminal. In someexamples, the first communication channel is the same as the secondcommunication channel. For example, the first and second communicationchannels can both be identified by the same multicast address, e.g., anEthernet or IPv4 multicast address. Some of the examples in thisparagraph can provide a virtual LAN, with the INVITE specifying avirtual lobby or group to join.

At 438, the control unit can make a third determination 440 that thesecond request 432 indicates a second predetermined media type (mtype)442. Examples are discussed herein, e.g., with reference to operation410. In some examples, the second mtype 442 is not an audio media type,and the second mtype 442 is not a video media type. Examples arediscussed herein, e.g., with reference to first mtype 414.

At 444, the control unit can make a fourth determination 446 that thesecond request 432 is associated with a second authorized user. Examplesare discussed herein, e.g., with reference to operation 416. The secondauthorized user can be the same as the first authorized user, or can bea different user. In some examples, operation 444 is performed beforeoperation 438 instead of after.

At 448, the control unit can send a second setup message 450 via thecommunications interface to the policy-management device 126. Thecontrol unit can send the second setup message 450 in response to thethird determination 440 and to the fourth determination 446. Examplesare discussed herein, e.g., with reference to operation 420. The secondsetup message 450 can request establishment of the second SB 434. Thesecond setup message 450 can include a second QoS indicator 452. SecondQoS indicator 452 can be the same (e.g., have the same value) as thefirst QoS indicator 424, or can be different therefrom.

At 454, the control unit can send, to the second network terminal, asecond completion message 456 indicating establishment of the second SB434. Examples are discussed herein, e.g., with reference to operation426. As discussed above with reference to operation 426, the controlunit can send the second completion message 456 independently of anyother terminals 102 that may be attached/attaching to the secondcommunication channel (#436) or communicating thereby.

In some examples, the second request 432 identifies the first networkterminal 102. For example, second request 432 from terminal 102(N) canidentify terminal 102(1). In some examples, second request 432 caninclude a network address or hostname of the first network terminal 102,or an MSISDN or other identifier of a user or subscriber associated withthe first network terminal 102. This can permit establishing a virtualLAN via SBs 406, 434, with the first network terminals 102 hosting thevirtual LAN and other terminal(s) 102 joining the virtual LAN.

FIG. 5 is a dataflow diagram illustrating an example process 500 forbearer management and related data items. Process 400 can be performed,e.g., by a server 304 of a telecommunications system 300, e.g.,including communications interface 322 and at least one processor 324.Server 304 can be or include, e.g., a policy-management device 126 suchas PCRF 218. In some examples, the server 304 includes control unit(s)configured to perform operations described below, e.g., in response tocomputer program instructions of the bearer-management module 328. Insome examples, operation 502 is performed before operation 506; in otherexamples, operation 506 is performed before operation 502.

At 502, the control unit can create the first specialized bearer (SB)406 having first QoS characteristics 504 in response to the first setupmessage 422. In some examples, operation 502 can include receiving thefirst setup message 422 from the bearer-management device 122. Operation502 can include, e.g., sending messages to a routing device 108 such asPGW 216. Operation 502 can include sending a Diameter Gx Re-Auth-Request(RAR) or CC-Answer (CCA) command from PCRF 218 to PGW 216, in someexamples. The RAR or CCA can include a QoS-Information AVP (3GPP TS29.212 v15.3.0 § 4.5.5.0, § 5.3.16, § 5.3.17), e.g., as discussed hereinwith reference to first QoS indicator 424.

In some examples, the first SB 406 permits exchange of first databetween the first network terminal 102 and at least one of the one ormore routing devices 108 (e.g., PGW 216). In some examples, the firstQoS characteristics 504 are associated with the first QoS indicator 424.

In some examples, the first SB 406 is not a VoLTE bearer; and the firstSB 406 is not a ViLTE bearer. For example, the QCI of first SB 406 canbe other than 1, 2, or 5.

At 506, the control unit can create the second SB 434 having second QoScharacteristics 508 in response to the second setup message 450. In someexamples, operation 502 can include receiving the second setup message450 from the bearer-management device 122. Examples are discussedherein, e.g., with reference to operation 502.

In some examples, the second SB 434 permits exchange of second databetween the second network terminal and at least one of the one or morerouting devices 108, e.g. routing device 108(1) or 108(M). In someexamples, the first SB 406 and the second SB 434 are connected to thesame routing device 108. In some examples, the first SB 406 and thesecond SB 434 are connected to respective, different routing devices108. In some examples, the second QoS characteristics 508 are associatedwith the second QoS indicator 452. Examples are discussed herein, e.g.,with reference to the first QoS characteristics 504.

In some examples, the second SB 434 is not a VoLTE bearer; and thesecond SB 434 is not a ViLTE bearer. Examples are discussed herein,e.g., with reference to the first SB 406 and the first QoScharacteristics 504.

FIG. 6 is a dataflow diagram illustrating an example process 600performed by server(s) 304 for bearer management and related data items.In some examples, server(s) 304, e.g., a bearer-management device 122,include control unit(s) In some examples, the server 304 includescontrol unit(s) configured to perform operations described below, e.g.,in response to computer program instructions of the bearer-managementmodule 328 or the session-operations module 330. For example, operation624 can be performed by the session-operations module 330 and theremaining operations can be performed by the bearer-management module328. Alternatively, all the operations of process 400 can be performedby the bearer-management module 328.

In some examples, process 600 cooperates with processes 700 and 800. Thedivision of operations between FIGS. 6-8 illustrates some exampleconfigurations and is not limiting. For example, a single physicaldevice may implement virtual P-CSCF, PCRF, and PGW functions, and soperform all the operations of processes 600, 700, and 800. In someexamples, operations of process 400 are performed before (as shown) orat least partly in parallel with operations of process 600.

At 602, the control unit of bearer-management device 122 can receive,from a third network terminal 102 via a communications interface, athird request 604 to create a third specialized bearer (SB) 606. Thethird request can identify at least one of the first communicationchannel or the second communication channel. For example, the thirdrequest 604 can include the identification 408 or the identification436. Examples are discussed herein, e.g., with reference to operation402.

At 608, the control unit can make a fifth determination 610 that thethird request 604 indicates a third predetermined media type (“mtype”)612. Examples are discussed herein, e.g., with reference to operation410.

In some examples, the third mtype 612 is not an audio media type, andthe third mtype 612 is not a video media type. Examples are discussedherein, e.g., with reference to first mtype 414.

At 614, the control unit can make a sixth determination 616 that thethird request 604 is associated with a third authorized user. Examplesare discussed herein, e.g., with reference to operation 416.

At 618, the control unit can send a third setup message 620 via thecommunications interface to the policy-management device 126. Thecontrol unit can send the third setup message 620 in response to thefifth determination 610 and to the sixth determination 616. The thirdsetup message 620 can request establishment of the third SB 606. Thethird setup message 620 can include a third QoS indicator 622. Examplesare discussed herein, e.g., with reference to operation 420 and firstsetup message 422. Operation 618 can be followed by operation 702, FIG.7.

At 624, the control unit can send, to the third network terminal 102, athird completion message 626 indicating establishment of the third SB606. Examples are discussed herein, e.g., with reference to operation426.

FIG. 7 is a dataflow diagram illustrating an example process 700performed by server(s) 304 for bearer management (e.g., creation) andrelated data items. In some examples, server(s) 304, e.g., apolicy-management device 126, include control unit(s) configured toperform operations described below, e.g., in response to computerprogram instructions of the bearer-management module 328. In someexamples, operation 702 can follow operation 618.

At 702, the control unit of the policy-management device 126 can createthe third specialized bearer (SB) 606 having third QoS characteristics704 in response to the third setup message 620. The third SB 606 canpermit exchange of third data between the third network terminal 102 andat least one of the one or more routing devices 108. The third QoScharacteristics 704 can be associated with the third QoS indicator 622.Examples are discussed herein, e.g., with reference to operation 502 andfirst QoS characteristics 504.

FIG. 8 is a dataflow diagram illustrating an example process 800performed by server(s) 304 for data exchange, and related data items. Insome examples, server(s) 304, e.g., a routing device 108, includecontrol unit(s) configured to perform operations described below, e.g.,in response to computer program instructions of the session-operationsmodule 330. In some examples, operations 802-808 can be performed afterall of operations 502, 506, and 702. In some examples, operation 802 canbe performed after operation 502; operation 806 can be performed afteroperations 502 and 506; or operation 808 can be performed afteroperations 502 and 702. In some examples, operation 808 can be performedor at least partly in parallel with operation 806.

At 802, the control unit of the routing device 108 can receive a packet804 via the first specialized bearer (SB or “S.B.”) 406. For example,the control unit can receive packet 804 from a first terminal 102, e.g.,via an EPS bearer associated with first SB 406. Packet 804 can becarried or over, or tunneled via, an S5/S8 interface from a servinggateway (SGW) or other routing device 108.

At 806, the control unit can forward the packet 804 to the second SB434. For example, the control unit can transmit the packet 804, or acopy or version thereof, via an S5/S8 interface or tunnel towards thesecond SB 434. This can be done using, e.g., IP routing based on routingtables exchanged by exterior gateway protocols or interior gatewayprotocols.

At 808, the control unit can forward the packet 804 to the third SB 606.Examples are discussed herein, e.g., with reference to operation 806.Although the figure references packet 804 three times, forwarding of thepacket 804 at operations 806 and 808 can include sending data notidentical to packet 804.

Various examples using at least one of FIGS. 6-8, e.g., all of FIGS.6-8, can provide virtual-LAN routing between at least three terminals,each of which is associated with a respective, different SB (e.g., SBs114, 116). This can permit exchange of low-latency traffic among groupsof terminals 102.

FIG. 9 is a dataflow diagram illustrating an example process 900performed by server(s) 304 for data exchange or routing, and relateddata items. In some examples, server(s) 304, e.g., routing device(s)108, include control unit(s) configured to perform operations describedbelow, e.g., in response to computer program instructions of thesession-operations module 330. In some examples, at least: operation 902can be performed after operation 502; operation 920 can be performedafter operation 506; operation 802 can include operation 902; operation806 can include operations 906 and 912; operation 808 can includeoperations 906 and 912; operation 806 can include operations 916 and920; or operation 808 can include operations 916 and 920.

In some examples, the one or more routing devices 108 include a firstrouting device 108(1) and a second, different routing device 108(M). Insome examples, the first routing device 108(1) performs operations902-912. In some examples, the second routing device 108(M) performsoperations 914-920.

At 902, the control unit of the first routing device 108(1) can receivea first packet 904 from the first network terminal, e.g., terminal102(1). Examples are discussed herein, e.g., with reference to operation802. For example, the control unit can receive the packet via the firstspecialized bearer (SB) 406.

At 906, the control unit of the first routing device 108(1) candetermine a second packet 908 based at least in part on the firstpacket, the second packet comprising a differentiated-services indicator910 associated with the first QoS characteristics 504. Thedifferentiated-services indicator 910 can be or include, e.g., an IPDSCP, Precedence, or Type of Service (ToS) value. For example, thecontrol unit can use a stored table to determine a DSCP based on the QCIof the first SB 406 or other information in the first QoS indicator 424.An example of such a table is GSMA FCM.01 v2.0 (October 2014) § 3.7.4,Table 3. In some examples, the stored table used by the control unitincludes at least one value not found in FCM.01. In some examples notshown, the first terminal 102(1) includes a differentiated-servicesindicator in the first packet 904 before sending first packet 904.

At 912, the control unit of the first routing device 108(1) can send thesecond packet 908 to the second routing device 108(M). In some examples,the control unit can send the second packet 908 over bearer 120 betweenrouting device 108(1) and routing device 108(M). Examples are discussedherein, e.g., with reference to operation 806. Operation 912 can precedeoperation 914.

At 914, the control unit of the second routing device 108(M) can receivethe second packet 908, e.g., via a network interface configured toreceive packets via bearer 120.

At 916, the control unit of the second routing device 108(M) candetermine a third packet 918 based at least in part on the second packet908. Examples are discussed herein, e.g., with reference to operation806. For example, third packet 918 may exclude thedifferentiated-services indicator 910 or include a differentdifferentiated-services indicator than differentiated-services indicator910. Additionally or alternatively, third packet 918 may have anincreased hop count or decreased time-to-live compared to second packet908. Additionally or alternatively, third packet 918 may differ fromsecond packet 908 in the presence or value of at least one header orfield.

At 920, the control unit of the second routing device 108(M) can sendthe third packet 918 to the second network terminal, e.g., terminal102(N). Examples are discussed herein, e.g., with reference to operation806.

FIG. 10 is a dataflow diagram illustrating an example process 1000 forbearer management and related data items. Process 1000 can be performed,e.g., by a server 304 of a telecommunications system 300, e.g.,including communications interface 322 and at least one processor 324.Server 304 can be or include, e.g., a bearer-management device 122 suchas P-CSCF 220, or a policy-management device 126 such as PCRF 218. Insome examples, the server 304 includes control unit(s) configured toperform operations described below, e.g., in response to computerprogram instructions of the bearer-management module 328.

At 1002, the control unit can receive, via a communications interfacefrom a network terminal 102, a first request 1004 to create a firstspecialized bearer (SB) 1006. Examples are discussed herein, e.g., withreference to operation 402, first request 404, and first SB 406. Thefirst request 1004 (e.g., a SIP INVITE) can indicate a user, e.g., byincluding identification information 1008 of the user. For example,identification information 1008 can be or include a value of a SIP From:or P-Asserted-Identity: header, a Gx User-CSG-Information AVP, a GxUser-Equipment-Info AVP, or a network address or address/port pairassociated with the user. Examples are discussed herein, e.g., withreference to operation 416. In some examples, the control unit is acontrol unit of a P-CSCF 220 or an AS 228, and the identificationinformation 1008 includes a SIP From: or P-Asserted-Identity: header orheader value. In some examples, the control unit is a control unit of aPCRF 218, and the identification information 1008 includes a Gx AVP orvalue such as those listed earlier in this paragraph.

The first request 1004 can indicate a first media type 1010 differentfrom an audio media type. For example, the first request 1004 canindicate the first media type 1010 as a value in a SIP Content-Typeheader, an SDP m=line, an Rx Media-Type AVP, a Gx Bearer-Usage AVP(e.g., value ≥2; cf. 3GPP 29.212 § 5.3.1), or a Gx Priority-Level AVP(e.g., the value being associated with low-latency data services).Examples are discussed herein, e.g., with reference to first mtype 414.

At 1012, the control unit can determine that the user is authorized tocreate the first SB, e.g., that the user's account carries authorizationfor creation of SBs on behalf of that account. Examples are discussedherein, e.g., with reference to operation 416.

At 1014, the control unit can send, in response, via the communicationsinterface to a policy-management device, a first setup message 1016requesting creation of the first SB 1006. The first setup message 1016can include a first QoS indicator 1018 associated with the first mediatype 1010. Examples are discussed herein, e.g., with reference tooperation 420, first setup message 422, and first QoS indicator 424.

FIG. 11 is a dataflow diagram illustrating an example process 1100 forbearer management and related data items. In some examples, controlunit(s) of server(s) 304, e.g., a bearer-management device 122 or apolicy-management device 126, perform operations described below, e.g.,in response to computer program instructions of the bearer-managementmodule 328. In some examples, operations of process 1100 can beperformed after or at least partly in parallel with operations ofprocess 1000. For example, operation 1104 can be performed afteroperation 1002 or 1014.

In some examples, first request 1004 identifies a channel 1102. Examplesare discussed herein, e.g., with reference to first communicationchannel identification 408.

At 1104, the control unit can receive, from the communications interfacefrom a network terminal, a second request 1106 to create a secondspecialized bearer (SB) 1108. The second request 1106 can identify thechannel 1102. The second request 1106 can indicate a second user, e.g.,by including identification information 1110. The second request 1106can indicate a second media type 1112, which can be different from anaudio media type and different from the first media type 1010. Examplesare discussed herein, e.g., with reference to operation 430 and secondmtype 442.

At 1114, the control unit can determine that the second user isauthorized to create the second SB 1108. Examples are discussed herein,e.g., with reference to operations 444 and 1012.

At 1116, the control unit can send, via the communications interface tothe policy-management device 126, a second setup message 1118 requestingcreation of the second SB 1108. Operation 1116 can be performed inresponse to the determination at operation 1114. The second setupmessage 1118 can include a second QoS indicator 1120 associated with thesecond media type 1112.

Various examples of process 1100 provide multiple SBs for a particularsession or channel. This can permit, e.g., different types ofinteractions between users or terminals 102 in a session to be carriedusing SBs having different QCIs. For example, a computer-mediatedcompetition might involve the exchange of both state informationrequiring low latency and contextual information (such as virtual timeof day) capable of tolerating higher latency Using multiple SBs in thisand other examples can permit using network resources more effectivelythan schemes in which all traffic is given low-latency treatment, whichcan increase network robustness and capacity.

FIG. 12 is a dataflow diagram illustrating an example process 1200 forbearer management or session management, e.g., creation or teardown ofbearers or sessions, and related data items. In some examples, controlunit(s) of server(s) 304, e.g., a P-CSCF 220 or other bearer-managementdevice 122 or policy-management device 126, perform operations describedbelow, e.g., in response to computer program instructions of thesession-operations module 330 or the bearer-management module 328. Insome examples, operations 1202-1218 are performed by session-operationsmodule 330. Alternatively, operations 1202-1212 can be performed bysession-operations module 330 and operations 1216-1218 bybearer-management module 328. Alternatively, operations 1202-1216 can beperformed by session-operations module 330 and operation 1218 bybearer-management module 328. In some examples, operation 1002 can befollowed by operation 1202.

At 1202, the control unit can establish, in response to the firstrequest 1004, a first session 1204 associated with the first specializedbearer (SB) 1006. This can be done, e.g., using SIP procedures forestablishment of dialogs in response to a SIP INVITE. The control unitcan record information about the session in a memory.

At 1206, the control unit can receive, after sending the first setupmessage 1016, a first termination request 1208. For example, the firsttermination request 1208 can include a SIP BYE request. In response, thecontrol unit can perform operations 1210 and 1212.

At 1210, the control unit can terminate the first session 1204. Forexample, the control unit can perform SIP dialog teardown procedures.The control unit can update or remove memory-stored information aboutthe session.

At 1212, the control unit can send, via the communications interface tothe policy-management device 126, a first teardown message 1214requesting removal of the first SB 1006. The first teardown message 1214can include, e.g., a Diameter CCR, ASR, or STR message (e.g., 29.213v15.3.0 § 4.2).

In some examples, multiple bearers are used, e.g., as discussed hereinwith reference to FIG. 11. Some of these examples manage the multiplebearers as a group using operations 1216 and 1218. Operation 1206, 1210,or 1212 can be followed by operation 1216.

At 1216, the control unit can determine that the first SB 1006 has beenterminated. In some examples, the control unit can receive a DiameterCCR or ASR associated with the first SB 1006, or another messageindicating that first SB 1006 has been terminated.

At 1218, the control unit can terminate the second SB. Operation 1218can be performed in response to the determination at operation 1216.Examples are discussed herein, e.g., with reference to operations 1210and 1212.

In some examples, responding to SB termination by terminating other SBs,e.g., associated with the same session (e.g., first session 1204), cansimulate a LAN failure in which all connectivity is lost. This canreduce the probability of data loss or corruption in an application dueto successful transmission of only some types of data, and thereforeimprove networked-application robustness. In some examples, operations1216 and 1218 can be performed at terminal 102 instead of or in additionto at server 304.

FIG. 13 is a dataflow diagram illustrating example processes 1300 forbearer management and related data items. In some examples, controlunit(s) of server(s) 304, e.g., a bearer-management device 122 or apolicy-management device 126, perform operations described below, e.g.,in response to computer program instructions of the bearer-managementmodule 328 or the session-operations module 330. In some examples,operation 1012 can include operations 1302 and 1306. In some examples,operation 1012 can be followed by operation 1308 or operation 1310. Insome examples, operation 1308 or 1314 can be followed by operation 1014.In some examples, operation 1014 can include operation 1308. In someexamples, operation 1014 can include operations 1310 and 1314.

At 1302, the control unit can retrieve, from information server 124,profile information 1304 associated with the user indicated in firstrequest 1004, e.g., identified by identification information 1008.Examples are discussed herein, e.g., with reference to operation 416.For example, profile information 1304 can include an AVP indicatingauthorization to create specialized bearers (SBs). Operation 1302 caninclude retrieving the profile information 1304 via Diameter or otherprotocols over the Sp reference point. For example, the control unit cansend a Diameter UDR to information server 124, and receive a DiameterUDA including multiple AVPs.

At 1306, the control unit can determine that the profile information1304 indicates that the user is authorized to create the first SB 1006.Examples are discussed herein, e.g., with reference to operation 416.For example, the control unit can determine that a predetermined AVP inprofile information 1304 includes a value representing the authorizationto create the first SB 1006.

In some examples of operations 1302 and 1306, the control unit is acontrol unit of PCRF 218. Some prior schemes do not retrieve and processuser-specific authorization data as described above with reference tooperations 1302 and 1306. See, e.g., 29.213 v15.3.0 Figure 4.1.1, NOTE2. In other examples, the control unit is a control unit of P-CSCF 220or AS 228.

At 1308, the control unit can determine the first setup message 1016further comprising a differentiated services indicator, e.g., a DSCP,associated with the first media type 1010. Examples are discussedherein, e.g., with reference to operation 906 anddifferentiated-services indicator 910. This can permit the routingdevice 108 to correctly prioritize packets traveling on bearer 120.

At 1310, the control unit can determine a packet filter 1312, e.g., atraffic flow template (TFT), based at least in part on the first mediatype 1010. For example, the control unit can determine Flow-DescriptionAVPs to provision to PCRF 218 via a Diameter connection over the Rxinterface or to routing device 108 (e.g., a PGW) via a Diameterconnection over the Gx interface. Operation 1310 can include determiningthe packet filter 1312 listing at least: a network address of theterminal 102; a network port (see, e.g., operation 1406, below); oridentification information described herein with reference to channel1102.

At 1314, the control unit can determine the first setup message 1016comprising the packet filter 1312. The packet filter 1312 can beassociated with the first SB 1006. For example, the first setup message1016 can be a Diameter AAR including the AVP(s) of the packet filter1312.

FIG. 14 is a dataflow diagram illustrating an example process 1400 fordata transfer using specialized bearers (SBs), and related data items.In some examples, control unit(s) of terminals(s) 102, 202, 302, performoperations described below, e.g., in response to computer programinstructions of the specialized application 318. In some examples, thecontrol unit(s) include at least one processor 310. The control unit cancommunicate via a wireless communications interface 314.

At 1402, the control unit can receive a network address 1404 via thewireless communications interface. The network address 1404 can beassociated with a particular APN, in some examples. For example, thecontrol unit can receive the network address 1404 in an Attach Acceptmessage from an MME upon initial attachment to an LTE network 306.Additionally or alternatively, the control unit can receive the networkaddress 1404 in a Non-Access Stratum (NAS) Activate default EPS bearercontext request message sent in response to a NAS PDN connectivityrequest.

At 1406, the control unit can determine a network port 1408 associatedwith the network address. For example, the control unit can select anunused network port, e.g., in the range 1024-65535. Operation 1406 canbe performed by application-level or OS-level modules. For example,operation 1406 can be carried out by the OS as part of processing of abind( ) call.

At 1410, the control unit can send a SIP INVITE message 1412 to anetwork control device. The SIP INVITE message 1412 can indicate thenetwork port 1408 and a media type 1414. In some examples, the mediatype 1414 is not an audio media type, and the media type 1414 is not avideo media type. The network port 1408 can be indicated on an m=line ofan SDP body of the SIP INVITE message 1412.

At 1416, the control unit can receive a SIP success message 1418 inresponse to the SIP invite message. SIP success message 1418 caninclude, e.g., a SIP 2xx response.

At 1420, the control unit can exchange (e.g., transmit or receive) dataon the network port 1408 with a peer network terminal (e.g., peer node210) via the wireless communications interface. This can be donesubsequent to receiving the SIP success message 1418. In some examples,the network port 1408 is indicated in a TFT or other packet filter 1312,FIG. 13. For example, the radio or related components of terminal 102can assign data to be transmitted over the network port 1408 to a firstSB 114, 1006 based on a match between network port 1408 and a portindicated in packet filter 1312. Some examples omit operation 1406 andinstead extract the network port 1408 from the packet filter 1312 afterreceiving SIP success message 1418.

In some prior VoLTE schemes and some other prior RTP-based schemes,exactly one protocol is used on a particular network port. For example,a SIP INVITE including an SDP body includes m=and a=rtpmap linesspecifying candidate protocols, and the SIP offer-answer model includesselecting exactly one of the offered candidates for a particular m=line.By contrast, in some examples, the exchanging data (operation 1420)includes multiplexing data in at least two protocols on the network port1408. For example, operation 1420 can include multiplexing a mediastream and a file-transfer stream. Multiplexing can be done usingtunneling protocols such as IPsec, TLS, GTP, or Proxy Mobile IP (PMIP).Additionally or alternatively, multiplexing can be done using layer 5-7tunneling protocols such as BEEP. This can permit virtual-LANcommunications, e.g., by multiplexing traffic over multiple networkports on a virtual adapter over a single network port 1408, e.g.,associated with an SB.

Some prior schemes, such as some VoLTE implementations, require that theSIP request URI or To: header identify the party with whomcommunications are to be carried out. Various examples herein permitmore flexible traffic exchange. For example, terminals 102(1) and102(N), FIG. 1, can be connected via SB 114, bearer 120, and SB 116 in avirtual-LAN configuration that routes communications between terminals102(1) and 102(N) without requiring each terminal 102(1), 102(N) toidentify the other. Similarly, some examples provide a virtual-LANconfiguration involving more than two terminals. A SIP INVITE message1412 for a channel is directed to the bearer-management device 122 orother network control device without requiring the addresses of otherterminal(s) that may be participating in that channel. For example, theSIP INVITE message 1412 can list AS 228 (e.g., acomputer-mediated-competition server) in the To: header and P-CSCF 220in the start-line. However, data can be sent via the resulting SB to aterminal 102 that is neither the AS 228 nor the P-CSCF 220.

Accordingly, in some examples, the SIP INVITE message 1412 comprises arequest URI indicating a first network entity, e.g., identified by nameor URI. In some examples, SIP INVITE message 1412 includes a To-headervalue indicating a second network entity. In some examples, the peernetwork terminal is different from the first network entity, and thepeer network terminal is different from the second network entity.

FIG. 15 is a dataflow diagram illustrating an example process 1500 forbearer management and related data items. In some examples, controlunit(s) of server(s) 304, e.g., a bearer-management device 122 or apolicy-management device 126, perform operations described below, e.g.,in response to computer program instructions of the specializedapplication 318. In some examples, operation 1502 is performed afteroperation 1402 or 1406. Various examples of FIG. 15 use multiplespecialized bearers (SBs) for respective, different types of traffic,e.g., as discussed herein with reference to operation 1116.

At 1502, the control unit can determine a second network port 1504associated with the network address 1404. Examples are discussed herein,e.g., with reference to operation 1406.

At 1506, the control unit can send a second SIP INVITE message 1508 tothe network control device. Examples are discussed herein, e.g., withreference to operation 1410. In some examples, the second SIP INVITEmessage indicates the second network port 1504 and the second SIP INVITEmessage indicates a second media type 1510. In some examples, the secondmedia type 1510 is not an audio media type, the second media type 1510is not a video media type, and the second media type 1510 is differentfrom the media type 1414.

At 1512, the control unit can receive a second SIP success message 1514in response to the SIP INVITE message 1508. Examples are discussedherein, e.g., with reference to operation 1416.

At 1516, the control unit can exchange data on the second network port1504 with the peer network terminal via the wireless communicationsinterface. Examples are discussed herein, e.g., with reference tooperation 1420. For example, the radio or related components of terminal102 can assign data to be transmitted over the second network port 1504to a second SB 1108 based on a match between second network port 1504and a port indicated in packet filter 1312 or another packet filter.

FIG. 16 is a dataflow diagram illustrating an example process 1600 forbearer management or data exchange, and related data items. In someexamples, control unit(s) of terminals(s) 102 perform operationsdescribed below, e.g., in response to computer program instructions ofthe specialized application 318. In some examples, operation 1602 isperformed after operation 1410. In some examples, operation 1420includes operation 1608.

At 1602, the control unit can receive, after sending the SIP INVITEmessage 1412, a TFT 1604 from the network control device. The TFT 1604can indicate a specialized bearer (SB) 1606 associated with the wirelesscommunications interface. For example, the TFT 1604 can be or include apacket filter 1312.

At 1608, the control unit can send at least some of the data via the SB1606 in response to the TFT 1604. For example, at layers below the IPlayer (e.g., layers 1 or 2, or LTE PHY or MAC layers such as RRC orPDCP), data can be mapped onto the SB 1606 if that data or itstransmission characteristics (e.g., layer 3 port) matches criteria inTFT 1604.

FIG. 17 is a dataflow diagram illustrating an example process 1700 forbearer management and related data items. In some examples, controlunit(s) of terminal(s) 102 perform operations described below, e.g., inresponse to computer program instructions of the specialized application318. In some examples, operation 1410 can include operation 1706. Insome examples, latency-sensitive traffic is carried on a different APNor network subset than the IMS APN. In some examples, operations 1402and 1702 can be performed in either relative order

At 1702, the control unit can receive a second network address 1704 viathe wireless communications interface. Examples are discussed herein,e.g., with reference to 1402. The second network address 1704 can bedifferent from the network address 1404.

At 1706, the control unit can send the SIP INVITE message 1412 via thesecond network address 1704. Examples are discussed herein, e.g., withreference to operation 1410.

In some examples, the second network address 1704 is associated with anIMS APN, e.g., the IMS well-known APN or another APN, and the networkaddress 1404 is associated with a second APN different from the IMS APN.The second APN can be an APN for low-latency communications. This canpermit separating signaling traffic from latency-sensitive data traffic,which can improve network management effectiveness. Moreover, in someexamples, the packet filter 1312 or TFT 1604 for the second APN passesall traffic on network address 1404. This can permit virtual-LANcommunications, in which terminal 102 can use any IP port on networkaddress 1404 for latency-sensitive communications. This can increasenetwork flexibility and resource utilization at the terminal 102.

Example Clauses

Various examples include one or more of, including any combination ofany number of, the following example features. Throughout these clauses,parenthetical remarks are for example and explanation, and are notlimiting. Parenthetical remarks given in this Example Clauses sectionwith respect to specific language apply to corresponding languagethroughout this section, unless otherwise indicated.

A: A system for telecommunication, the system comprising: one or morerouting devices; a bearer-management device comprising a communicationsinterface; and a policy-management device; wherein the bearer-managementdevice is configured to perform first operations comprising: receiving,from a first network terminal via a communications interface, a firstrequest to create a first specialized bearer, the first requestidentifying a first communication channel; making a first determinationthat the first request indicates a first predetermined media type,wherein: the first predetermined media type is not an audio media type;and the first predetermined media type is not a video media type; makinga second determination that the first request is associated with a firstauthorized user; sending, via the communications interface to apolicy-management device in response to the first determination and tothe second determination, a first setup message, wherein: the firstsetup message requests establishment of the first specialized bearer;and the first setup message comprises a first Quality of Service (QoS)indicator; sending, to the first network terminal, a first completionmessage indicating establishment of the first specialized bearer;receiving, from a second network terminal via the communicationsinterface, a second request to create a second specialized bearer, thesecond request identifying a second communication channel; making athird determination that the second request indicates a secondpredetermined media type, wherein: the second predetermined media typeis not an audio media type; and the second predetermined media type isnot a video media type; making a fourth determination that the secondrequest is associated with a second authorized user; sending, via thecommunications interface to the policy-management device in response tothe third determination and to the fourth determination, a second setupmessage, wherein: the second setup message requests establishment of thesecond specialized bearer; and the second setup message comprises asecond QoS indicator; sending, to the second network terminal, a secondcompletion message indicating establishment of the second specializedbearer; wherein the policy-management device is configured to performsecond operations comprising: creating the first specialized bearerhaving first QoS characteristics in response to the first setup message,wherein: the first specialized bearer permits exchange of first databetween the first network terminal and at least one of the one or morerouting devices; and the first QoS characteristics are associated withthe first QoS indicator; creating the second specialized bearer havingsecond QoS characteristics in response to the second setup message,wherein: the second specialized bearer permits exchange of second databetween the second network terminal and at least one of the one or morerouting devices; and the second QoS characteristics are associated withthe second QoS indicator; and wherein the one or more routing devicesare configured to convey traffic between the first specialized bearerand the second specialized bearer.

B: The system according to paragraph A, wherein: the first specializedbearer is not a voice-over-long-term-evolution (VoLTE) bearer; and thefirst specialized bearer is not a video-over-long-term-evolution (ViLTE)bearer,

C: The system according to paragraph A or B, wherein: the firstoperations further comprise: receiving, from a third network terminalvia the communications interface, a third request to create a thirdspecialized bearer, the third request identifying at least the firstcommunication channel or the second communication channel; making afifth determination that the third request indicates a thirdpredetermined media type, wherein: the third predetermined media type isnot an audio media type; and the third predetermined media type is not avideo media type; making a sixth determination that the third request isassociated with a third authorized user; sending, via the communicationsinterface to the policy-management device in response to the fifthdetermination and to the sixth determination, a third setup message,wherein: the third setup message requests establishment of the thirdspecialized bearer; and the third setup message comprises a third QoSindicator; sending, to the third network terminal, a third completionmessage indicating establishment of the third specialized bearer; thesecond operations further comprise: creating the third specializedbearer having third QoS characteristics in response to the third setupmessage, wherein: the third specialized bearer permits exchange of thirddata between the third network terminal and at least one of the one ormore routing devices; and the third QoS characteristics are associatedwith the third QoS indicator; and the one or more routing devices arefurther configured to: receive a packet via the first specializedbearer; forward the packet to the second specialized bearer; and forwardthe packet to the third specialized bearer.

D: The system according to any of paragraphs A-C, wherein the secondrequest identifies the first network terminal.

E: The system according to any of paragraphs A-D, wherein: the one ormore routing devices comprise a first routing device and a second,different routing device; the first routing device is configured to:receive a first packet from the first network terminal; determine asecond packet based at least in part on the first packet, the secondpacket comprising a differentiated-services indicator associated withthe first QoS characteristics; and send the second packet to the secondrouting device; and the second routing device is configured to: receivethe second packet; determine a third packet based at least in part onthe second packet; and send the third packet to the second networkterminal.

F: The system according to any of paragraphs A-E, the first operationscomprising making the second determination at least partly byretrieving, from an information server, authorization informationassociated with user information included in the first request.

G: The system according to any of claims A-F, wherein the firstcommunication channel is communicatively connected with the secondcommunication channel.

H: The system according to any of claims A-G, wherein the identification(408) is not an identifier of a party reachable via VoLTE or ViLTE fromthe server (304).

I: The system according to any of claims A-H, wherein the identification(408) is not an identifier of a party reachable via VoLTE or ViLTE fromthe first network terminal (102, 202, 302).

J: The system according to any of paragraphs A-I, wherein: at least oneof the one or more routing devices comprises a Long-Term Evolution (LTE)packet data network gateway (PGW); the policy-management devicecomprises at least an LTE policy charging and rules function (PCRF); andthe bearer-management device comprises at least an LTE proxy callsession control function (P-CSCF), Application Server (AS), or PCRF.

K: The system according to any of paragraphs A-J, wherein the firstspecialized bearer comprises an LTE data radio bearer (DRB).

L: A method comprising, by a network control device: receiving, via acommunications interface from a network terminal, a first request tocreate a first specialized bearer, wherein the first request indicates auser and indicates a first media type different from an audio mediatype; determining that the user is authorized to create the firstspecialized bearer; and in response, sending, via the communicationsinterface to a policy-management device, a first setup messagerequesting creation of the first specialized bearer, the first setupmessage comprising a first Quality of Service (QoS) indicator associatedwith the first media type.

M: The method according to paragraph L, wherein: the first requestidentifies a channel; and the method further comprises, by the networkcontrol device: receiving, from the communications interface from anetwork terminal, a second request to create a second specializedbearer, wherein: the second request identifies the channel; the secondrequest indicates a second user; the second request indicates a secondmedia type; the second media type is different from an audio media type;and the second media type is different from the first media type;determining that the second user is authorized to create the secondspecialized bearer; and in response, sending, via the communicationsinterface to the policy-management device, a second setup messagerequesting creation of the second specialized bearer, the second setupmessage comprising a second QoS indicator associated with the secondmedia type.

N: The system according to paragraph M, further comprising, by thenetwork control device: determining that the first specialized bearerhas been terminated; and in response, terminating the second specializedbearer.

O: The method according to any of paragraphs L-N, further comprising, bythe network control device: in response to the first request,establishing a first session associated with the first specializedbearer; after sending the first setup message, receiving a firsttermination request; and in response: terminating the first session; andsending, via the communications interface to the policy-managementdevice, a first teardown message requesting removal of the firstspecialized bearer.

P: The method according to any of paragraphs L-O, further comprising, bythe network control device: determining a packet filter based at leastin part on the first media type; and determining the first setup messagecomprising the packet filter, wherein the packet filter is associatedwith the first specialized bearer.

Q: The method according to any of paragraphs L-P, further comprising, bythe network control device, determining the first setup message furthercomprising a differentiated services indicator associated with the firstmedia type.

R: The method according to any of paragraphs L-Q, wherein: the networkcontrol device is a policy control rules function (PCRF) node; and themethod comprises, by the network control device: retrieving, from aninformation server, profile information associated with the user; anddetermining that the profile information indicates that the user isauthorized to create the first specialized bearer.

S: A network terminal, comprising: a wireless communications interface;at least one processor; and at least one computer-readable mediumstoring instructions executable by the at least one processor to causethe at least one processor to perform operations comprising: receiving anetwork address via the wireless communications interface; determining anetwork port associated with the network address; sending a SessionInitiation Protocol (SIP) INVITE message to a network control device,wherein: the SIP INVITE message indicates the network port; the SIPINVITE message indicates a media type; the media type is not an audiomedia type; and the media type is not a video media type; receiving aSIP success message in response to the SIP invite message; andsubsequently, exchanging data on the network port with a peer networkterminal via the wireless communications interface.

T: The network terminal according to paragraph S, wherein: the SIPINVITE message comprises: a request Uniform Resource Identifier (URI)indicating a first network entity; and a To-header value indicating asecond network entity; the peer network terminal is different from thefirst network entity; and the peer network terminal is different fromthe second network entity.

U: The network terminal according to paragraph S or T, the operationsfurther comprising: determining a second network port associated withthe network address; sending a second Session Initiation Protocol (SIP)INVITE message to the network control device, wherein: the second SIPINVITE message indicates the second network port; the second SIP INVITEmessage indicates a second media type; the second media type is not anaudio media type; the second media type is not a video media type; andthe second media type is different from the media type; receiving asecond SIP success message in response to the SIP INVITE message; andsubsequently, exchanging data on the second network port with the peernetwork terminal via the wireless communications interface.

V: The network terminal according to any of paragraphs S-U, theoperations further comprising: receiving, after sending the SIP INVITEmessage, a traffic-flow template (TFT) from the network control device,the TFT indicating a specialized bearer associated with the wirelesscommunications interface; and sending at least some of the data via thespecialized bearer in response to the TFT.

W: The network terminal according to any of paragraphs S-V, theoperations further comprising: receiving a second network address viathe wireless communications interface, wherein the second networkaddress is different from the network address; and sending the SIPINVITE via the second network address.

X: The network terminal according to paragraph W, wherein: the secondnetwork address is associated with an Internet Protocol (IP) MultimediaSubsystem (IMS) Access Point Name (APN); and the network address isassociated with a second APN different from the IMS APN.

Y: The network terminal according to any of paragraphs S-X, wherein theexchanging data comprises multiplexing data in at least two protocols onthe network port.

Z: The system according to any of paragraphs A-K, component(s) of thesystem further configured to perform the functions recited in any ofparagraphs L-R.

AB: The subject matter of any of paragraphs A-K, L-R, or S-Y, whereinthe specialized bearer(s) are assigned to QCI(s) between one and four,or to QCIs having priority levels within the range of priority levelsspanned by QCIs one through four.

AC: A device comprising: a processor; and a computer-readable medium,e.g., a computer storage medium, having thereon computer-executableinstructions, the computer-executable instructions upon execution by theprocessor configuring the device to perform operations as any ofparagraphs A-K, L-R, or S-Y recites.

AD: A computer-readable medium, e.g., a computer storage medium, havingthereon computer-executable instructions, the computer-executableinstructions upon execution configuring a computer to perform operationsas any of paragraphs A-K, L-R, or S-Y recites.

AE: A device comprising: a processor; and a computer-readable medium,e.g., a computer storage medium, having thereon computer-executableinstructions, the computer-executable instructions upon execution by theprocessor configuring the device to perform operations as any ofparagraphs A-K, L-R, or S-Y recites.

AF: A system comprising: means for processing; and means for storinghaving thereon computer-executable instructions, the computer-executableinstructions including means to configure the system to carry out amethod as any of paragraphs A-K, L-R, or S-Y recites.

AG: A network control device configured to perform operations as any ofparagraphs A-K, L-R, or S-Y recites.

AH: A method comprising performing operations as any of paragraphs A-K,L-R, or S-Y recites.

CONCLUSION

Many variations and modifications can be made to the above-describedexamples, the elements of which are to be understood as being amongother acceptable examples. All such modifications and variations areintended to be included herein within the scope of this disclosure andprotected by the claims. Moreover, this disclosure is inclusive ofcombinations of the aspects described herein. References to “aparticular aspect” (or “embodiment” or “version”) and the like refer tofeatures that are present in at least one aspect of the invention.Separate references to “an aspect” (or “embodiment”) or “particularaspects” or the like do not necessarily refer to the same aspect oraspects; however, such aspects are not mutually exclusive, unless soindicated or as are readily apparent to one of skill in the art. The useof singular or plural in referring to “method” or “methods” and the likeis not limiting.

The methods, processes, or operations described above can be embodiedin, and fully automated via, software code modules executed by one ormore computers or processors. As used herein, the term “module” isintended to represent example divisions of the described operations(e.g., implemented in software or hardware) for purposes of discussion,and is not intended to represent any type of requirement or requiredmethod, manner or organization. Therefore, while various “modules” arediscussed herein, their functionality and/or similar functionality canbe arranged differently (e.g., combined into a smaller number ofmodules, broken into a larger number of modules, etc.). In someinstances, the functionality and/or modules discussed herein may beimplemented as part of a computer operating system (OS). In otherinstances, the functionality and/or modules may be implemented as partof a device driver, firmware, application, or other software subsystem.

Example computer-implemented operations described herein canadditionally or alternatively be embodied in specialized computerhardware, e.g., FPGAs. For example, various aspects herein may take theform of an entirely hardware aspect, an entirely software aspect(including firmware, resident software, micro-code, etc.), or an aspectcombining software and hardware aspects. These aspects can all generallybe referred to herein as a “service,” “circuit,” “circuitry,” “module,”or “system.”

The word “or” and the phrase “and/or” are used herein in an inclusivesense unless specifically stated otherwise. Accordingly, conjunctivelanguage such as, but not limited to, at least one of the phrases “X, Y,or Z,” “at least X, Y, or Z,” “at least one of X, Y or Z,” “one or moreof X, Y, or Z,” and/or any of those phrases with “and/or” substitutedfor “or,” unless specifically stated otherwise, is to be understood assignifying that an item, term, etc. can be either X, or Y, or Z, or acombination of any elements thereof (e.g., a combination of XY, XZ, YZ,and/or XYZ). Any use herein of phrases such as “X, or Y, or both” or “X,or Y, or combinations thereof” is for clarity of explanation and doesnot imply that language such as “X or Y” excludes the possibility ofboth X and Y, unless such exclusion is expressly stated.

As used herein, language such as “one or more Xs” shall be consideredsynonymous with “at least one X” unless otherwise expressly specified.Any recitation of “one or more Xs” signifies that the described steps,operations, structures, or other features may, e.g., include, or beperformed with respect to, exactly one X, or a plurality of Xs, invarious examples, and that the described subject matter operatesregardless of the number of Xs present, as long as that number isgreater than or equal to one.

Conditional language such as, among others, “can,” “could,” “might” or“may,” unless specifically stated otherwise, are understood within thecontext to present that certain examples include, while other examplesdo not include, certain features, elements and/or steps. Thus, suchconditional language is not generally intended to imply that certainfeatures, elements and/or steps are in any way required for one or moreexamples or that one or more examples necessarily include logic fordeciding, with or without user input or prompting, whether certainfeatures, elements and/or steps are included or are to be performed inany particular example.

In the claims, any reference to a group of items provided by a precedingclaim clause is a reference to at least some of the items in the groupof items, unless specifically stated otherwise. This document expresslyenvisions alternatives with respect to each and every one of thefollowing claims individually, in any of which claims any such referencerefers to each and every one of the items in the corresponding group ofitems. Furthermore, in the claims, unless otherwise explicitlyspecified, an operation described as being “based on” a recited item canbe performed based on only that item, or based at least in part on thatitem. This document expressly envisions alternatives with respect toeach and every one of the following claims individually, in any of whichclaims any “based on” language refers to the recited item(s), and noother(s). Additionally, in any claim using the “comprising” transitionalphrase, a recitation of a specific number of components (e.g., “two Xs”)is not limited to embodiments including exactly that number of thosecomponents, unless expressly specified (e.g., “exactly two Xs”).However, such a claim does describe both embodiments that includeexactly the specified number of those components and embodiments thatinclude at least the specified number of those components.

What is claimed is:
 1. A system for telecommunication, the systemcomprising: one or more routing devices; a bearer-management devicecomprising a communications interface; and a policy-management device;wherein the bearer-management device is configured to perform firstoperations comprising: receiving, from a first network terminal via acommunications interface, a first request to create a first specializedbearer, the first request identifying a first communication channel;making a first determination that the first request indicates a firstpredetermined media type, wherein: the first predetermined media type isnot an audio media type; and the first predetermined media type is not avideo media type; making a second determination that the first requestis associated with a first authorized user; sending, via thecommunications interface to a policy-management device in response tothe first determination and to the second determination, a first setupmessage, wherein: the first setup message requests establishment of thefirst specialized bearer; and the first setup message comprises a firstQuality of Service (QoS) indicator; sending, to the first networkterminal, a first completion message indicating establishment of thefirst specialized bearer; receiving, from a second network terminal viathe communications interface, a second request to create a secondspecialized bearer, the second request identifying a secondcommunication channel; making a third determination that the secondrequest indicates a second predetermined media type, wherein: the secondpredetermined media type is not an audio media type; and the secondpredetermined media type is not a video media type; making a fourthdetermination that the second request is associated with a secondauthorized user; sending, via the communications interface to thepolicy-management device in response to the third determination and tothe fourth determination, a second setup message, wherein: the secondsetup message requests establishment of the second specialized bearer;and the second setup message comprises a second QoS indicator; sending,to the second network terminal, a second completion message indicatingestablishment of the second specialized bearer; wherein thepolicy-management device is configured to perform second operationscomprising: creating the first specialized bearer having first QoScharacteristics in response to the first setup message, wherein: thefirst specialized bearer permits exchange of first data between thefirst network terminal and at least one of the one or more routingdevices; and the first QoS characteristics are associated with the firstQoS indicator; creating the second specialized bearer having second QoScharacteristics in response to the second setup message, wherein: thesecond specialized bearer permits exchange of second data between thesecond network terminal and at least one of the one or more routingdevices; and the second QoS characteristics are associated with thesecond QoS indicator; and wherein the one or more routing devices areconfigured to convey traffic between the first specialized bearer andthe second specialized bearer.
 2. The system according to claim 1,wherein: the first specialized bearer is not avoice-over-long-term-evolution (VoLTE) bearer; and the first specializedbearer is not a video-over-long-term-evolution (ViLTE) bearer,
 3. Thesystem according to claim 1, wherein: the first operations furthercomprise: receiving, from a third network terminal via thecommunications interface, a third request to create a third specializedbearer, the third request identifying at least the first communicationchannel or the second communication channel; making a fifthdetermination that the third request indicates a third predeterminedmedia type, wherein: the third predetermined media type is not an audiomedia type; and the third predetermined media type is not a video mediatype; making a sixth determination that the third request is associatedwith a third authorized user; sending, via the communications interfaceto the policy-management device in response to the fifth determinationand to the sixth determination, a third setup message, wherein: thethird setup message requests establishment of the third specializedbearer; and the third setup message comprises a third QoS indicator;sending, to the third network terminal, a third completion messageindicating establishment of the third specialized bearer; the secondoperations further comprise: creating the third specialized bearerhaving third QoS characteristics in response to the third setup message,wherein: the third specialized bearer permits exchange of third databetween the third network terminal and at least one of the one or morerouting devices; and the third QoS characteristics are associated withthe third QoS indicator; and the one or more routing devices are furtherconfigured to: receive a packet via the first specialized bearer;forward the packet to the second specialized bearer; and forward thepacket to the third specialized bearer.
 4. The system according to claim1, wherein the second request identifies the first network terminal. 5.The system according to claim 1, wherein: the one or more routingdevices comprise a first routing device and a second, different routingdevice; the first routing device is configured to: receive a firstpacket from the first network terminal; determine a second packet basedat least in part on the first packet, the second packet comprising adifferentiated-services indicator associated with the first QoScharacteristics; and send the second packet to the second routingdevice; and the second routing device is configured to: receive thesecond packet; determine a third packet based at least in part on thesecond packet; and send the third packet to the second network terminal.6. The system according to claim 1, the first operations comprisingmaking the second determination at least partly by retrieving, from aninformation server, authorization information associated with userinformation included in the first request.
 7. A method comprising, by anetwork control device: receiving, via a communications interface from anetwork terminal, a first request to create a first specialized bearer,wherein the first request indicates a user and indicates a first mediatype different from an audio media type; determining that the user isauthorized to create the first specialized bearer; and in response,sending, via the communications interface to a policy-management device,a first setup message requesting creation of the first specializedbearer, the first setup message comprising a first Quality of Service(QoS) indicator associated with the first media type.
 8. The methodaccording to claim 7, wherein: the first request identifies a channel;and the method further comprises, by the network control device:receiving, from the communications interface from a network terminal, asecond request to create a second specialized bearer, wherein: thesecond request identifies the channel; the second request indicates asecond user; the second request indicates a second media type; thesecond media type is different from an audio media type; and the secondmedia type is different from the first media type; determining that thesecond user is authorized to create the second specialized bearer; andin response, sending, via the communications interface to thepolicy-management device, a second setup message requesting creation ofthe second specialized bearer, the second setup message comprising asecond QoS indicator associated with the second media type.
 9. Themethod according to claim 8, further comprising, by the network controldevice: determining that the first specialized bearer has beenterminated; and in response, terminating the second specialized bearer.10. The method according to claim 7, further comprising, by the networkcontrol device: in response to the first request, establishing a firstsession associated with the first specialized bearer; after sending thefirst setup message, receiving a first termination request; and inresponse: terminating the first session; and sending, via thecommunications interface to the policy-management device, a firstteardown message requesting removal of the first specialized bearer. 11.The method according to claim 7, further comprising, by the networkcontrol device: determining a packet filter based at least in part onthe first media type; and determining the first setup message comprisingthe packet filter, wherein the packet filter is associated with thefirst specialized bearer.
 12. The method according to claim 7, furthercomprising, by the network control device, determining the first setupmessage further comprising a differentiated services indicatorassociated with the first media type.
 13. The method according to claim7, wherein: the network control device is a policy control rulesfunction (PCRF) node; and the method comprises, by the network controldevice: retrieving, from an information server, profile informationassociated with the user; and determining that the profile informationindicates that the user is authorized to create the first specializedbearer.
 14. A network terminal, comprising: a wireless communicationsinterface; at least one processor; and at least one computer-readablemedium storing instructions executable by the at least one processor tocause the at least one processor to perform operations comprising:receiving a network address via the wireless communications interface;determining a network port associated with the network address; sendinga Session Initiation Protocol (SIP) INVITE message to a network controldevice, wherein: the SIP INVITE message indicates the network port; theSIP INVITE message indicates a media type; the media type is not anaudio media type; and the media type is not a video media type;receiving a SIP success message in response to the SIP invite message;and subsequently, exchanging data on the network port with a peernetwork terminal via the wireless communications interface.
 15. Thenetwork terminal according to claim 14, wherein: the SIP INVITE messagecomprises: a request Uniform Resource Identifier (URI) indicating afirst network entity; and a To-header value indicating a second networkentity; the peer network terminal is different from the first networkentity; and the peer network terminal is different from the secondnetwork entity.
 16. The network terminal according to claim 14, theoperations further comprising: determining a second network portassociated with the network address; sending a second Session InitiationProtocol (SIP) INVITE message to the network control device, wherein:the second SIP INVITE message indicates the second network port; thesecond SIP INVITE message indicates a second media type; the secondmedia type is not an audio media type; the second media type is not avideo media type; and the second media type is different from the mediatype; receiving a second SIP success message in response to the SIPINVITE message; and subsequently, exchanging data on the second networkport with the peer network terminal via the wireless communicationsinterface.
 17. The network terminal according to claim 14, theoperations further comprising: receiving, after sending the SIP INVITEmessage, a traffic-flow template (TFT) from the network control device,the TFT indicating a specialized bearer associated with the wirelesscommunications interface; and sending at least some of the data via thespecialized bearer in response to the TFT.
 18. The network terminalaccording to claim 14, the operations further comprising: receiving asecond network address via the wireless communications interface,wherein the second network address is different from the networkaddress; and sending the SIP INVITE via the second network address. 19.The network terminal according to claim 18, wherein: the second networkaddress is associated with an Internet Protocol (IP) MultimediaSubsystem (IMS) Access Point Name (APN); and the network address isassociated with a second APN different from the IMS APN.
 20. The networkterminal according to claim 14, wherein the exchanging data comprisesmultiplexing data in at least two protocols on the network port.